Artificial intelligence systems that incorporate expert knowledge related to hypertension treatments

ABSTRACT

Provided is a process, including: obtaining test data that quantifies a patient&#39;s cardiovascular status, the test data specifying patient attributes in a plurality of cardiovascular dimensions of the patient; determining a plurality of normalized differences between the test data and target criteria in each of the cardiovascular dimensions; determining predicted-effect vectors of each of a plurality of different classes of pharmaceuticals; determining an aggregate score for each respective class of pharmaceuticals among the different classes of pharmaceuticals based on values of the corresponding predicted-effect vectors; ranking the different classes of pharmaceuticals based on the aggregate scores; and outputting a recommended sequence of pharmaceuticals to administer.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent claims the benefit of U.S. Provisional Pat. App. 62/888,928,titled ARTIFICIAL INTELLIGENCE SYSTEMS THAT INCORPORATE EXPERT KNOWLEDGERELATED TO HYPERTENSION TREATEMENTS, filed 19 Aug. 2019. The entirecontent of each afore-mentioned patent filing is hereby incorporated byreference for all purposes.

BACKGROUND 1. Field

The present disclosure relates generally to artificial intelligence (AI)and, more specifically, to AI systems that incorporate expert knowledgerelated to the management and care of patients with hypertension whileretaining the ability to generalize to provide appropriate responses tonovel inputs.

2. Description of the Related Art

Physicians and other medical practitioners contend with an enormousamount of complexity when treating patients. A significant amount ofthat complexity is involved in selecting the medications that can besthelp a specific patient and that patient's vast array of specificvariables. Often, doctors have to make decisions under uncertainty basedupon relatively noisy, high dimensional data about patients, and thosesignals can evolve over time, and some cases in ways that are difficultto predict.

Medical practitioners are trained in and are taught to know and apply anenormous body of medical research to select the appropriateinterventions for patients. At this point in time there areapproximately 800,000 new medical journal articles published per year.In order to win Food and Drug Administration (FDA) approval everymedication must be tested in studies that are carefully constructed andexecuted under FDA supervision and approval. Subsequent studies of thesame drug may occur under independent auspices or sponsored by the drugmanufacturer. Each study has a certain set of inclusionary andexclusionary variables. Different studies of the same drug can and oftendo have different inclusion and exclusion variables and values. Whenphysicians go to prescribe a drug, it is unlikely that they can recallfrom memory which studies investigated that condition or that drug andextremely unlikely that to recall any of the inclusion and exclusionvariables. Thus, determining which drug to use is very difficult.

To assist those in the field, on occasion teams of experts are convenedunder the authority of different national or international authoritieslike the American College of Cardiology, the American Heart Association,the Institute of Medicine, etc. to sort out the various studies relatedto a specific disease state and to update the science that is availablewith regard to that disease state concluding with high level findings.After hundreds of thousands of pages of published scientific papers, forexample, a body might establish a standard of care sometimes called “TheEvidence Based Standard of Care” (EBS). At a minimum an EBS or anotherstandard will define, in some fields, a standard by which successfultherapy or treatment can be measured, e.g., a goal for therapy andgeneral comments about a variety of tools one could use to achieve thatgoal. But these standards can be challenging to implement, become out ofdate, or apply less granular heuristics to favor administrability overprecision.

Given these challenges, only very recently have developers and computerscience researchers begun to attempt to help doctors choose theappropriate course of treatments for patients, and many of theseattempts to date have been limited to diseases like cancer. Theseattempts, however, have not been met with success generally. Someapproaches have attempted to apply expert systems that encode theuniverse of medical knowledge in a collection of rules. The problem withrules are that the number of variables combined with the way thatvariables can interact and the number of solution options can approachtens of millions of permutations, which is beyond the capability forrule making. In general, expert systems have proven too brittle, unableto generalize outside of scenarios explicitly contemplated by the systemarchitect. Such systems often struggle with patients presenting novelscenarios. On the other hand, some researchers have attempted to trainmodels with relatively large numbers of degrees of freedom, like deepneural networks, on historical records of treatments and patientresponses. These systems, however, often fail to benefit from theknowledge produced by medical research and in many cases have arelatively low training efficiency. These models struggle with smallertraining sets and training sets in which samples are sparse in areas inwhich the model may be later requested to perform. There is also theproblem that medical data is often extremely noisy and filled witherror.

SUMMARY

The following is a non-exhaustive listing of some aspects of the presenttechniques. These and other aspects are described in the followingdisclosure.

Some aspects include a process including: obtaining, with a computersystem, data from one or multiple tests that, for example, quantifies apatient's cardiovascular functional status, the test data specifyingpatient attributes in a plurality of cardiac, vascular andcardiovascular dimensions of the patient, a first subset of theplurality of cardiovascular dimensions being independent cardiovasculardimensions and a second subset of the plurality of dimensions beingdependent cardiovascular dimensions; determining, with the computersystem, a plurality of normalized differences between the test data andtarget criteria in each of the cardiovascular dimensions, the pluralityof normalized differences quantifying different aspects of hypertensionof the patient; determining, with the computer system, predicted-effectvectors of each of a plurality of different classes of pharmaceuticalshaving hypertension as an indication, wherein: the predicted-effectvectors each correspond to a different respective class ofpharmaceuticals among the different classes of pharmaceuticals, thepredicted-effect vectors each have a plurality of values quantifyingrespective effects of the corresponding class of pharmaceuticals oncorresponding dimensions among a third set of the cardiovasculardimensions of the patient, the values are each based on both thecorresponding normalized differences of the corresponding dimensionamong the third set and a respective strength of effect of thecorresponding class of pharmaceuticals on the corresponding dimension,the respective strength effects are determined based on respectivemulti-dimensional models of the corresponding class of pharmaceuticals,and the third set at least overlaps with the first subset and the secondsubset; determining, with the computer system, an aggregate score foreach respective class of pharmaceuticals among the different classes ofpharmaceuticals based on values of the corresponding predicted-effectvectors of the corresponding class of pharmaceuticals; ranking, with thecomputer system, the different classes of pharmaceuticals based on theaggregate scores to form a ranked list of the different classes ofpharmaceuticals; and outputting, with the computer system, based on theranking, a recommended sequence of the classes of pharmaceuticals toadminister to the patient.

Some aspects include a tangible, non-transitory, machine-readable mediumstoring instructions that when executed by a data processing apparatuscause the data processing apparatus to perform operations including theabove-mentioned process.

Some aspects include a system, including: one or more processors; andmemory storing instructions that when executed by the processors causethe processors to effectuate operations of the above-mentioned process.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-mentioned aspects and other aspects of the present techniqueswill be better understood when the present application is read in viewof the following figures in which like numbers indicate similar oridentical elements:

FIG. 1 is a logical architecture block diagram of aknowledge-representing medical-recommendation AI application inaccordance with some embodiments of the present techniques;

FIG. 2 is a flowchart of a medical-intervention recommendation processfor hypertension that may be implemented with the logical architectureof FIG. 1 in accordance with some embodiments of the present techniques;and

FIG. 3 is a block diagram of an example of a computing device upon whichthe application of FIG. 1 and process of FIG. 2 may be executed inaccordance with some embodiments of the present techniques.

While the present techniques are susceptible to various modificationsand alternative forms, specific embodiments thereof are shown by way ofexample in the drawings and will herein be described in detail. Thedrawings may not be to scale. It should be understood, however, that thedrawings and detailed description thereto are not intended to limit thepresent techniques to the particular form disclosed, but to thecontrary, the intention is to cover all modifications, equivalents, andalternatives falling within the spirit and scope of the presenttechniques as defined by the appended claims.

DETAILED DESCRIPTION OF CERTAIN EMBODIMENTS

To mitigate the problems described herein, the inventors had to bothinvent solutions and, in some cases just as importantly, recognizeproblems overlooked (or not yet foreseen) by others in the field ofartificial intelligence. Indeed, the inventors wish to emphasize thedifficulty of recognizing those problems that are nascent and willbecome much more apparent in the future should trends in industrycontinue as the inventors expect. Further, because multiple problems areaddressed, it should be understood that some embodiments areproblem-specific, and not all embodiments address every problem withtraditional systems described herein or provide every benefit describedherein. That said, improvements that solve various permutations of theseproblems are described below.

Some embodiments mitigate some of the above-described issues with anartificial intelligence application that encodes knowledge from medicalresearch in a collection of models responsive to patients states inrelatively large envelopes of relatively high dimensional patient-statespaces. As a result, the models are expected to be less brittle thanrules in an expert system, while still capturing medical knowledge fromrelevant literature in the field. Further, the models are expected to bemore training-data efficient than naïve applications of machine learningmodels that do not benefit from expert knowledge. None of which is tosuggest that use of the present techniques in conjunction with expertsystems or such machine learning models is disclaimed or the any othersubject matter discussed herein is disclaimed.

The present techniques are described with reference to recommendinginterventions for hypertension, but it should be emphasized that thepresent computing techniques are expected to have application in a widevariety of fields having similar properties to the discussed use cases.As recently as thirty-years ago there were few medications to treathypertension and many patients died or suffered major complications(e.g., strokes, heart attacks, Transient Ischemic Attacks (TIAs), renalfailure, etc.) caused by their uncontrolled blood pressures. In thosedays the physician would try the few available drugs to reduce bloodpressure. Often, though, blood pressure could not be controlled.

Over the intervening years there has been enormous research intohypertension—and most of the other, common chronic diseases—resulting ina deeper, more complex understanding about the diseases, their causesand various factors or variables related to those disease. Theadditional knowledge, in turn, resulted in the development of many moretherapies. In 2019 there are more than twelve classes of drugs that canbe used to treat hypertension and, within, those classes, there areoften multiple different drugs per class, each slightly different fromthe others within the same class.

As mentioned, an EBS or other standard may define a standard by whichsuccessful therapy or treatment can be measured, e.g., a goal fortherapy and general comments about a variety of tools one could use toachieve that goal. For instance, in hypertension, a blood pressure of<139/89 (also expressed as <140/90) is considered controlled and a bloodpressure that is >140/90 is considered “uncontrolled” and therefore moredangerous to the patient by several authorities. Other authorities haveargued persuasively for a blood pressure as low as <130/80, so there isno universal consensus in some cases.

The Centers for Disease Control (CDC) states that a goal of <140/90 is aminimal standard for control of hypertension. The Centers for Medicareand Medicaid (CMS) requires that providers must report the percentage ofall their adult patients who are less than 85 years old with a diagnosisof hypertension that are below 140/90 and this is percent is a measureof physician success as a treater of hypertension. The CDC also reportsthat only about half of US patients with hypertension achieve the saferlevel of blood pressure <140/90.

A blood pressure reading typically includes both the systolic anddiastolic blood pressure (i.e., systolic/diastolic). These are highorder measures. The systolic and diastolic pressures are the result of acascade of “cause and effect” relationships. Not all of theserelationships are completely understood or known by medicine but manyare. For example, blood pressure is determined in part by variousperformance characteristics of the heart, blood vessels and fluidstatus. The heart's functions, blood vessel functions or the fluidstatus of the patient are, in turn, influenced or determined by manyneuro-hormonal, bio-chemical, mechanical, age, race, genetic and othervariables.

It is possible to treat a patient in a manner that the desired end pointblood pressure is achieved but other cardiac, vascular, fluid variablesare unacceptably out-of-range. In such an instance the patient's care issub-optimized despite having a “good” blood pressure (e.g., below140/90) because, while the overall blood pressure meets the EBS of care,the underlying parameters are not ideal. This can occur, for instance,when one variable is over-treated and another variable undertreatedresulting in an “average” blood pressure that is at the acceptablelevels. In these instances, there may be ongoing harm to the patient'soverall current or future health status despite the blood pressure beingin the desired range.

Another set of variables is that a specific patient with high bloodpressure may have any of a significant number of comorbidities which canindividually or in combination determine which therapies can or cannotbe used effectively or safely. There are a variety of potential effectsof co-morbidities to a treatment strategy including:

-   -   a. Co-morbidities can promote the use of certain agents or        therapies;    -   b. Co-morbidities can alter the therapeutic characteristics of        agents or therapies rendering them more or less effective;    -   c. Co-morbidities can eliminate the possibility of using certain        therapies;    -   d. Co-morbidities can change the prioritization or order of        using therapies;    -   e. Co-morbidities can cause certain potential problems which        then have to be evaluated as therapies are added; and    -   f. Co-morbidities can alter or change entirely the therapeutic        end-points for a disease.

In some instances, the effect of one co-morbidity points therapy in onedirection while a second co-morbidity points therapy in the oppositedirection and this conflict must be resolved based upon some evaluationof the weight of various factors.

The evolution of scientific knowledge that has resulted in recognitionof all these patient attributes that drive blood pressure has led to themultiplication of therapies including the hundreds of drugs that existtoday but did not even thirty or fewer years ago.

Thus, treating hypertension implicates the above-described complexity.It is worth keeping in mind that, as of 2019, there are over 800,000scientific medical articles published per year. This is a tremendousamount of information for a human-actor to absorb. In blood pressuretreatment, the role of the physician or other licensed care provider isto calculate all or as many of the above-mentioned variables as possiblein order to determine both effective as well as optimal therapy for aspecific patient. There are literally tens of millions of permutationsinvolved when you consider all the cardio-vascular, demographic,pharmacological and co-morbid conditions. This complexity is more thaneven a very intelligent person can manage in her head. It is believedthat this is an underlying reason why the success rate in hypertensionis as low as 50% on average. What happens often is that patients whopresent with the most common forms of hypertension and who do not have alot of complications or co-morbidities are most likely to besuccessfully treated while the more complex cases are very oftenunsuccessfully treated.

To manage this level of extreme complexity, some embodiments implementan AI system described below with reference to FIGS. 1 and 2 on one ormore computing devices like that described below with reference to FIG.3 . Some embodiments obtain each specific hypertension patient's“starting point”—e.g., all of the medically-available variables thatinfluence the patient's current blood pressure state—and then determinea (often multi-step) route to the desired outcome (e.g., an end pointblood pressure, aligning the other cardiac, vascular and fluid metricsand take into consideration all of the comorbidities) via optimalmedication therapy.

Embodiments determine this route in a different way from previousapplications of AI to recommend medical interventions. A rules engine,standing alone, is believed to be unsuitable for this task. The varietyof permutations of patient states is simply too large, making an expertsystem brittle to the type of novel inputs expected to be encounteredwith regularity. Also, a commercially-feasible rules engine would not beable to consider various combination or interaction effects which alsoarise.

Embodiments determine this route through what is believed to be afundamentally different approach to how a human would undertake theanalysis. General AI is not available, and there is no documentedalgorithm universally implemented by physicians. The way humans makethese decisions is believed to be based on some combination of Bayesiananalysis and rough heuristics as a short-cut for accounting for theavailable knowledge in the field. The result, as an empirical matter, issub-optimal, and inferior to results obtained with the presenttechniques. As such, the present is necessarily different, in partbecause it is more performant, in part because it is more comprehensive,and in part because of the way knowledge in the field is systematized bymodels to make that knowledge usable to an AI system across a wide rangeof high-dimensional novel (in the sense that the state has not beeninput to the system before or was not part of a training set)patient-state inputs.

In some embodiments, the physiological status including heart function,vascular functions, vascular compliance and fluid levels may bedetermined. Many of these variables may be evaluated and measured asfunctions of each other. Thus, some variables are not absolute measures,common to all patients, and there is a combinatorial explosion ofpossible patient states when all medically useful variables areevaluated.

Some embodiments implement a cardiovascular model to define the cardiac,vascular and fluid forces in relationship to each other and as outcomes.With such models, measured patient attributes may be transformed intoother estimated or otherwise inferred patient attributes, in some casesbased on interactions of measured patient attributes, patientdemographic attributes, and comorbidities.

Some embodiments implement a drug-efficacy model that quantifies theeffectiveness and other performance characteristics of each drug or drugcombination against each of the various patterns generated by thecardio-vascular model as generated in the first step.

Some embodiments implement a comorbidity model to quantify theimplications of over 25 comorbidities and other factors that can changerecommendations in various ways.

Some of these models may implement one or more performance curves toquantify the effects of a specific given variable and interactiveperformance curves quantifying the effects of one or several variablescollectively or on a one-to-one basis.

In some embodiments, test data, such as diagnostic test data, are usedby the computer system to quantify the patient's cardiovascular status.The data may be plotted against multiple cardiovascular measurementscales. These measurement scales may be mathematically related to eachother in many cases. A subset may be independent. In some embodiments,four independent variables are the only inputs into drug class scoring:systolic blood pressure (S), pulse pressure (p), cardiac index (x), andheart rate (z).

The relative distances between the patient datum (or other collection ofattributes collectively representing patient state) and multiple targetcriteria may be calculated to quantify the different aspects ofhypertension. The various criteria may be heterogenous units-of-measureand have dramatically different scales. That is, for one measure valuesare commonly between 0.25 and 0.95, whereas another measure is between1500 and 6000. A scale rationalization (or other form of normalization)technique may be used to quantify the relative comparative magnitude ofdistances, resulting in all measures on a shared scale (e.g., of −3.0 to+3.0). In some embodiments, the shared scale may be a number of standarddeviations from target, like a mean of a population from which thestandard deviation is determined, like a z-score. A negative distancemeaning below or less than target and a positive distance meaning aboveor greater than target.

The test data may be processed to provide a patient's status, indicatingthe most important aspect of their hypertension and which variables needto move most and in which direction (increase/decrease).

In some embodiments, drug-efficacy models may be constructed toaccommodate the fact that different pharmaceutical agents or classesaffect different cardiovascular parameters. An analyses of theliterature and consultation with pharmacology specialist about bestmethods to interpret discrepancies could be used to construct a weightedscoring system, which may be applied to reflect the efficacy of the drugclass on a particular parameter. Example weights may be stored in amatrix with columns corresponding to drug class and rows correspondingto various cardiovascular parameters, like V, C, z, and Si. Differentdrug classes may have different weights for different cardiovascularparameters. An example of such a matrix is presented in the followingtable:

HTN drug class weighting scores parameter drug class A drug class B1drug class Cn V 4 0 3 C 0 3 4 z 0 4 2 Si 0 2 1The resulting score for a particular hypertension drug class may be thequantification of the cumulative net beneficial effect, which may becomputed with a variety of approaches, such as a weighted sum of thestrength of effect times the distance for each cardiovascular parameter.This approach may be used to score the various hypertension drug classesin a nearly-orthogonal array of possible patient data. With thisapproach, in some embodiments, models may be implemented for each drugclass. In some cases, the models may correspond to four or five orhigher dimensional non-planar surfaces with one output dimensions andseveral input dimensions corresponding to patient attributes.

With these models, some embodiments determine an aggregate a score foreach drug class given a unique set of independent inputs for thepatient. These scores may then be compared to each other to determinethe optimum hypertension drug treatment regimen.

Two additional processes may be applied by some embodiments to generatethe “ladder” of drug classes. The concept of the ladder is based onevidence that it often requires more than one drug class to effectivelycontrol hypertension. Additionally, often a patient is already takingthe recommended drug class. The provider then would decide to increasethe dosage of the top recommended drug class or add the next highestrecommended drug class. In some cases, a ladder may be expressed as asequence, which may specify one or more stages in which, during eachstage, one or more classes of drugs is to be administered to thepatient.

Most hypertension drug classes can be safely taken together. However,some combinations of drug classes should not be taken together. Forexample, drug classes Cd and Cn should not be taken together; same fordrug classes B1 and B3. The resulting list may be filtered to skip overdrug classes that are not to be taken in combination. The higher scoringdrug class may be the only one of a pair in conflict allowed to remainon the ladder.

In some embodiments, the cardiovascular scores may be modified given thepresence of certain comorbidities or demographic information about thehypertension patient. Some hypertension drug classes are contraindicatedfor specific medical conditions. For example, a given drug class A maybe contraindicated for pregnancy. In other cases, a drug class may havea very beneficial effect on a given comorbidity. For example, drug classA may have a positive influence when renal function or diabetes arepresent. In response to input indicating a potential comorbidity orrelated attribute, drug class scores of corresponding drug classes maybe adjusted accordingly. And in some cases, multiple clinical conditionscould be present and all have additive adjustments to the final drugclass score and its associated ranking in the ladder.

In some embodiments, the above techniques and related techniques may beimplemented in a computing environment shown in FIG. 1 . Aknowledge-representing medical-recommendation AI application 10 mayexecute on one of the computing devices described below with referenceto FIG. 3 , for example, in an operating system thereof, or on acollection of such computing devices, for example, with variouscomponents implemented as services in a service-oriented architecture.Or in some cases, the application 10 may be executed as a monolithicapplication on a single computing device, for example, as a singleprocess run on a single processor core.

In some embodiments, the application 10 may be configured to receiveinput from a doctor 12 about a patient 14 via a user input 16. In someembodiments, the application 10 may be configured to cause apresentation of information responsive to the input on a display 18,like a graphical user interface on a monitor, head-mounted display, orthe like, or via an audio display via speech-to-text conversion ofoutputs to audio conveyed via a speaker. Or in some embodiments, thedisplay 18 is implemented with a printer printing a printed page withoutputs.

The input 16 may include a keyboard, a microphone coupled to aspeech-to-text translator, a touchscreen, a mouse, or an applicationprogram interface of another application providing a set of inputs tothe application 10, for example, a patient record database configured toexport patient medical records to the application 10 responsive to aquery from the application 10 or other instructions from a medicalpractitioner.

In some embodiments, the application 10 may execute on a computingdevice in a doctor's office or hospital, and inputs and outputs may bereceived and provided without conveying information over a network forsecurity purposes, or in some cases, the application may be remotelyhosted and information may be conveyed while encrypted in transit.

In some embodiments, the application includes a test data ingest module20 configured to receive a patient record indicating a medical state ofthe patient at a given point in time. In some embodiments, the ingestmodule 20 may be configured to receive a plurality of such recordscorresponding to a history of states of the patient, each record havinga timestamp indicating a time at which the state was exhibited by thepatient. In some embodiments, the records may include a plurality ofattributes of the patient related to hypertension in variouscardiovascular dimensions. Some of the dimensions may be independentdimensions, like those listed above, and some of the dimensions may bedependent the dimensions that are caused, at least in part, by theindependent dimensions, and some cases through interactions thereof.Examples of such dimensions include the following:

S=systolic blood pressure (SBP)

D=diastolic blood pressure (DBP) p=pulse pressure (SBP−DBP)

y=mean arterial pressure (MAP=DBP+?p)

x=cardiac index (CI)

z=heart rate (HR/pulse {bpm})

V=total peripheral resistance index (TPRI=80*MAP/CI)

C=cardiac power index (CPI=0.0022*MAP*CI)

Si=stroke index (SI=1000*CI/HR)

In some embodiments, attributes of the patient and each of thesedimensions may be entered into a user interface presented on the display18, for example, in fields of the form by a medical technician afterhaving measured the various attributes of the patient. Or in some cases,the attributes may be received via an application program interface fromanother application, for example, in hierarchical data serializationformat.

In some cases, a set of received attributes may be transformed into alarger set of inferred attributes of the patient based on a patientmodel like those discussed above. For instance, some such models maymodel the patient with a causal graph, with input nodes corresponding toobservable attributes and edges and downstream causal nodes specifyingtransformations by which other patient attributes may be inferred, insome cases, based on interactions of observed or computed patientattributes.

Some embodiments may validate the patient record with validator 22. Insome embodiments, this may include determining that all requiredattributes (i.e., a value in a dimension) are present, that the receivedattributes are greater than a minimum possible value, and that thereceived attributes are less than a maximum possible value in therespective dimension. Upon determining that a given patient attribute isoutside of one of these ranges, some embodiments may emit an errormessage and present an input via display 18 inviting a medicalprofessional to confirm that the value is correct or change the entryvia input 16. Some embodiments may determine whether an attribute in apatient record is more than a threshold amount different from a previousattribute in the same dimension in a previous record, with outlierdifferences potentially indicating an erroneous entry. Again, someembodiments may signal and alarm and invite correction responsive todetecting such an event.

In some embodiments, after all of the patient record attributes arevalidated, the result may be advanced to the normalizer 24 in theillustrated pipeline of the application 10. In some embodiments, thenormalizer 24 may compute normalized differences between each patientattribute and a target value of that attribute in the attributesdimension. In some embodiments, these differences may be quantifiedrelative to population statistics of the respective attribute in apopulation, as reflected in the population model 26. For example, thenormalized attribute may be expressed as a z-score indicating an amountof standard deviations above or below a mean for the attribute in apopulation, as encoded in the population model 26. Some embodiments maycompute similar statistics for other types of non-Gaussiandistributions. Some embodiments may compute a percentage of thepopulation that is above the patient's attribute as measured in thegiven dimension and subtract 50 percentage points to center the resultaround zero. In some embodiments, normalized values for each attributemay have a negative value to indicate that the patient's attribute islower than is desired and a positive value to indicate that thepatient's attribute is higher than is desired. In some embodiments, thenormalized values may all be on the same scale, despite having measuredattributes in the patient record on different scales. In some cases,values may be normalized after subsequent transformations describedbelow, e.g., class models 28 described below may be calibrated tonon-normalized values, and outputs thereof may be normalized tofacilitate combination of values across various attributes withheterogenous units-of-measure and ranges.

In some embodiments, the population model 26 may characterize populationstatistics of attributes in each of the dimensions of the patientrecord. The characterization may take a variety of forms, including ahistogram, a measure of central tendency (like mean, median, and mode)and a measure of variation (like standard deviation or variance). Insome embodiments, the measure of central tendency may be a target valuefor the respective dimension of the patient's cardiovascular health. Insome embodiments, the population may be a known healthy population orreference population. In some cases, the target value may be determinedfrom the above-described EBS.

The output of the normalizer 24 may be a normalized patient recordhaving a plurality of normalized attributes in a plurality of differentcardiovascular dimensions. For example, the normalizer 24 may outputmore than four, more than six, or more than eight normalized valuesranging from −3 to +3 and each corresponding to a differentcardiovascular dimension of the patient.

The output of the normalizer 24 may be provided to a predictor 26, whichmay predict magnitudes and directions of effects of various classes ofpharmaceuticals that indicate for hypertension on the respectiveattributes in the corresponding dimensions of the patient'scardiovascular health. For example, the predictor may predict that afirst class of pharmaceuticals will decrease a first normalizedattribute by a first amount on the normalized scale and increase asecond normalized attribute by a second amount on the normalized scale,while a second class of pharmaceuticals may be predicted to decrease thefirst normalized attribute by a third amount on the normalized scale,have no effect on the second normalized attribute, and decrease a thirdnormalized attribute by a fourth amount on the normalized scale.

In some embodiments, the predictor 26 may determine a set of predictionsfor each of a plurality of different classes of pharmaceuticals thatindicate for hypertension. For example, nine different predictions fornine different cardiovascular dimensions may be determined for a firstclass of pharmaceuticals, and nine different predictions for the samenine different cardiovascular dimensions may be determined for a secondclass of pharmaceuticals. In some embodiments, each set of predictionsmay be characterized as a predicted-effect vector, which may specify alocation in a continuous vector space or discrete vector spacecorresponding to the cardiovascular dimensions of the patient. Programstate need not be labeled as a vector in program code to constitute avector, provided that the information of a vector is encoded. In someembodiments, the dimensions for which a prediction is made may be thesame as those for which data is obtained by the ingest module 20, or insome cases predictions may only made for a subset of those dimensions,such as just the independent cardiovascular dimensions.

In some embodiments, each predicted-effect vector may have a pluralityof values corresponding to predicted effects in each of the differentcardiovascular dimensions of the patient. In some embodiments, thevalues may indicate whether the predicted effect tends to drive thecorresponding attribute closer to the target in the cardiovasculardimension or further from the respective target. For example, anattribute that is below the target, but for which a predicted effecttends to increase the attribute to be closer to the target, may have avalue that is positive, while an attribute that is above the target andfor which the predicted effect tends to increase the attribute may havea value that is negative. In some embodiments, the resulting value maybe a difference between an absolute value of the attribute in thenormalized record and an absolute value of the attribute predicted tooccur upon application of the class of pharmaceuticals at issue. Makingan attribute further from his target become closer to his target maytend to correspond with a larger value and vice versa.

In some embodiments, the predictor 26 computes the predicted-effectvector based upon a corresponding one of the class model 28. In someembodiments, each class model 28 corresponds to a different class ofpharmaceuticals, or in some cases interactions between classes ofpharmaceuticals may also have their own class model. In someembodiments, each class model encodes a three, four, five, six, seven,or higher dimensional surface, indicating effects of the correspondingclass of pharmaceuticals in each of the cardiac dimensions for whichpredictions are made based upon the normalized state of the patientreceived from the normalizer 24. In some cases, these higher dimensionalmodels may be decomposed into lower dimensional slices, like a pluralityof different three-dimensional or four dimensional representations,which collectively still constitute the higher dimensional modelregardless of the lower dimensional encoding. In some cases, the modelshave an output dimension in each of the above-described cardiovasculardimensions and an input dimension in each of the above-describedcardiovascular dimensions. The surface may indicate how inputs map tooutputs for the respective class of drugs. The models may be formed bysynthesizing medical research, e.g., averaging empirical data acrossstudies, training a Markov chain Monte Carlo model with empiricalresults of such studies, based on application of results of one study toa model proven by another, interpolating between regimes examined indifferent studies, or the like. The models 28 may take a variety offorms. Examples include polynomial functions, or collections thereof.Other examples include lookup tables, support vector machines, neuralnetworks, and other lossy or lossless encodings of relationships betweeninputs and outputs.

In some case, a predicted effect matrix may be computed for each classof pharmaceuticals, with drug-specific predicted-effect vectors fordrugs within the class. Models 28 may be developed for different membersof a class. In some cases, a highest scoring drug within a class (basedon the following analysis) may be selected as the predicted-effectvector for that class, and that specific member of the class may berecommended.

In some embodiments, the predicted-effect vectors for each of thedifferent classes of pharmaceuticals may be output to the class scorer30, which may compute an aggregate score (e.g., a single ordinal orcardinal value) for each of the classes of pharmaceuticals based on someor all of the values in the respective corresponding predicted-effectvector for that class of pharmaceuticals. Or in some embodiments, scoresmay be computed for a plurality of different metrics, or someembodiments may compute a single aggregate score for each class, whichin some cases may be a sum of the computed values that serve as scalarsof the predicted-effect vector, or in some cases the aggregate score maybe a weighted sum of these values. Weights may be determined with avariety of techniques, including hand coding weights based uponknowledge of an expert in the field or empirical literature in thefield. The class scorer 30 may output a set of aggregate scores, e.g.,with one aggregate score for each of the different classes ofpharmaceuticals. The aggregate scores may indicate a preliminarysuitability of the respective class of pharmaceuticals for the patient,with larger scores indicating greater suitability and lower scoresindicating lower suitability. (Reference to signs of scores and othervalues should be read as also referring to semantic equivalents in whichsigns are inverted, for example, discussion of a score in which a highervalue indicates a desirable result should be read as equivalent todiscussion of a negative version of that score or an inverse of thatscore in which a lower value indicates the desired result.)

The set of scores for the class of pharmaceuticals may be received bythe comorbidity filter 32. In some embodiments, the scores may beadjusted based upon various comorbidities of the patient. For example,certain classes of pharmaceuticals may be documented in the literatureas having a negative effect or being precluded for patients having aparticular comorbidity, or some classes of pharmaceuticals may be moredesirable for some comorbidities. In some embodiments, the relationshipsmay be encoded as adjustment factors, such as sums added to the scoresor weights multiplied by the scores. For instance, a patient beingpregnant may cause a particular class of pharmaceuticals score to bemultiplied by 0.8 to indicate that the class of pharmaceuticals can havenegative effects, while another class of pharmaceuticals score may bemultiplied by 0 indicate that pregnant women are not to take that classof pharmaceuticals. The term filter is used to refer to this process ofadjustment, which in some cases may take the form of removing candidateclasses of pharmaceuticals or in other cases may take the form oftransforming the scores upon which those classes of pharmaceuticals areselected among.

Some embodiments may similarly apply a demographic filter 34, which mayapply similar adjustments based upon demographic attributes of thepatient, like race, gender, age, and the like.

Some embodiments may apply a compatibility filter 36 to the classes ofpharmaceuticals. Some embodiments may maintain a square matrix or otherdata structure encoding pairwise comparisons between the candidateclasses of pharmaceuticals with matrix values indicating whether thedifferent pairs of classes of pharmaceuticals indexed to those entriesare compatible with one another. Or some embodiments may encode a weightor sum to be applied as an adjustment to the above-describe scores whenthe pairs of pharmaceutical classes are used together (e.g.,concurrently, sequentially, or as part of the same sequence even if notsequentially, and some embodiments may apply a different compatibilitymatrix to each of these different types of relationships between classesof drugs in a course of treatment, for instance to identify those thatmay be grouped for concurrent use or should be taken sequentially). Someembodiments may detect pairs of pharmaceuticals that are not compatibleand remove from the candidate set a lower ranking member of the pair.

Some embodiments may implement a ranker 38 that may rank the resultingadjusted or otherwise filtered classes of pharmaceuticals based on thescores as transformed by components 30 through 36. In some embodiments,the operations implemented by these components may be executed in adifferent order from that depicted in the illustrated pipeline, which isnot to suggest that any other feature is limited to the arrangementshown. In some cases, ranking may include grouping classes ofpharmaceuticals to be taken concurrently, and in some cases, it mayinclude indicating groups of one or more to be taken serially, accordingto rank, e.g., starting from a highest-ranking class and workingdownward.

Some embodiments may then pass the resulting ordered list from theranker 38 to the user interface generator 40, which may generate a userinterface displaying the results through any of the types of displaysabove on display 18. In some embodiments, in the user interface, variousclasses of pharmaceuticals may be further annotated with data aboutspecific vulnerabilities or suitability of the patient for the class ofpharmaceuticals. For example, where a comorbidity causes an aggregatescore for a class of pharmaceuticals to be adjusted, in response, aprose description of the adjustment and rationale may be retrieved frommemory and presented in association with the class pharmaceuticals inthe user interface. Similarly, where classes of pharmaceuticals areprohibited or are incompatible, prose descriptions of warnings may beretrieved from memory in response to detecting that such events haveoccurred and presented in the user interface by the user interfacegenerator 40.

In some embodiments, the application of FIG. 1 may execute a process 50shown in FIG. 2 to recommend a course of interventions for hypertension,though embodiments of the process 50 are not limited to thatimplementation, which is not to suggest that any other feature describedherein is limiting in all embodiments. In some embodiments, thefunctionality of the process 50 and the other functionality describedherein, with the exception of administering treatments, may beimplemented as computer code stored in a tangible, non-transitory,machine-readable medium and executable on one or more processors, suchthat when that computer code is executed, the correspondingfunctionality is effectuated. In some embodiments, the describedoperations may be executed in a different order, additional steps may beinserted, some steps may be executed concurrently, some steps may beomitted, some steps may be repeated multiple times before advancing toother steps, and the process may otherwise be varied, which again is notto suggest that any other description herein is limiting.

Some embodiments of the process 50 include obtaining test data thatquantifies a patient's cardiovascular status, as indicated by block 52.In some embodiments, this may include obtaining the above-describedpatient record. In some embodiments, this patient record may be computedin part by applying measured attributes to a patient model to computedependent variables of the patient's cardiovascular health, for example,with a patient model configured to map those inputs into a correspondingoutput.

Some embodiments may determine whether there are additional dimensionsin the test data, as indicated by block 54. Upon determining that thereare additional dimensions, the process 50 in some embodiments may selectthe next dimension, as indicated by block 56. Some embodiments may thennormalize an attribute in the current cardiovascular dimension, asindicated by block 58, for instance, with the above-describednormalization techniques. Embodiments may then return to block 54 anddetermine whether there are more dimensions in the test data process.Upon determining that there are no more, some embodiments may proceed toblock 60 and determine whether there are more classes of pharmaceuticalsto process. Upon determining that there are, some embodiments may selectthe next class, as indicated by block 62.

Some embodiments may then select a class model of the current class, asindicated by block 64, for instance, among the above-described classmodels 28 in FIG. 1 . Some embodiments may then determine whether thereare more dimensions of a predicted-effect vector to process, asindicated by block 66. Upon determining that there are more dimensions,some embodiments may select the next dimension of the predicted-effectvector being computed, as indicated by block 68. Some embodiments maythen determine a strength of effect of the current class on the currentdimension with the current class model, as indicated by block 70.Embodiments may then return to block 66 to determine whether there aremore dimensions of the predicted-effect vector to process with thecurrent class model.

Upon determining that there are no more dimensions the process, in someembodiments, may proceed to select a subset of the classes based on theaggregate scores, as indicated by block 74. Some embodiments may thenobtain comorbidities of the patient, as indicated by block 76, andfilter the subset based on the comorbidities, as indicated by block 78.Again, filtering, as that term is used herein, may include adjustingrespective scores or removing from further consideration some classes ofpharmaceuticals. Some embodiments may then obtain demographic attributesof the patient, as indicated by block 80, and filter the subset based onthe demographic attributes, as indicated by block 82, for instance, withthe techniques described above. Some embodiments may further filter thesubset based on pair-wise incompatibility, as indicated by block 184,for instance, with the above-described compatibility filter 36. Someembodiments may proceed to rank the filtered subset, as indicated byblock 86, and present a recommended sequence of classes to administer tothe patient based on the ranking, as indicated by block 88, for example,in the above-described display 18 with the user interface generator 40.

In some embodiments, some of the following steps may be performed byphysician upon interacting with user interface. In some embodiments, thephysician may determine whether there are more steps in the recommendedsequence, as indicated by block 90. Upon determining that there are moresteps, the physician may select a next class of pharmaceuticals in thesequence, as indicated by block 92. The physician may then cause theselected class of pharmaceuticals to be administered to the patient, asindicated by block 94, for instance, over some duration of time, whichmay span more than a week or month, and spanning multiple office visitsin some cases. The physician may determine periodically whether toretest the patient, as indicated by block 96. Upon determining not toretest, the process may return to block 90 to determine whether thereare further steps in the sequence to administer to the patient. Upondetermining that there are no more steps in the sequence or upondetermining to not retest, as indicated in block 90 or 96, someembodiments may terminate the process if the patient is healthy orreturn to block 52 to update the sequence based upon updated testing ofthe patient.

In some embodiments, the above techniques may be implemented with aspecific approach described below in the following technicaldocumentation. It should be emphasized of the technical documentationdescribes a subset of embodiments and does not purport to characterizeall forms of implementation of the present approaches, which is not tosuggest that any other description is so limiting:

FIG. 3 is a diagram that illustrates an exemplary computing system 1000in accordance with embodiments of the present technique. Variousportions of systems and methods described herein, may include or beexecuted on one or more computer systems similar to computing system1000. Further, processes and modules described herein may be executed byone or more processing systems similar to that of computing system 1000.

Computing system 1000 may include one or more processors (e.g.,processors 1010 a-1010 n) coupled to system memory 1020, an input/outputI/O device interface 1030, and a network interface 1040 via aninput/output (I/O) interface 1050. A processor may include a singleprocessor or a plurality of processors (e.g., distributed processors). Aprocessor may be any suitable processor capable of executing orotherwise performing instructions. A processor may include a centralprocessing unit (CPU) that carries out program instructions to performthe arithmetical, logical, and input/output operations of computingsystem 1000. A processor may execute code (e.g., processor firmware, aprotocol stack, a database management system, an operating system, or acombination thereof) that creates an execution environment for programinstructions. A processor may include a programmable processor. Aprocessor may include general or special purpose microprocessors. Aprocessor may receive instructions and data from a memory (e.g., systemmemory 1020). Computing system 1000 may be a uni-processor systemincluding one processor (e.g., processor 1010 a), or a multi-processorsystem including any number of suitable processors (e.g., 1010 a-1010n). Multiple processors may be employed to provide for parallel orsequential execution of one or more portions of the techniques describedherein. Processes, such as logic flows, described herein may beperformed by one or more programmable processors executing one or morecomputer programs to perform functions by operating on input data andgenerating corresponding output. Processes described herein may beperformed by, and apparatus can also be implemented as, special purposelogic circuitry, e.g., an FPGA (field programmable gate array) or anASIC (application specific integrated circuit). Computing system 1000may include a plurality of computing devices (e.g., distributed computersystems) to implement various processing functions.

I/O device interface 1030 may provide an interface for connection of oneor more I/O devices 1060 to computer system 1000. I/O devices mayinclude devices that receive input (e.g., from a user) or outputinformation (e.g., to a user). I/O devices 1060 may include, forexample, graphical user interface presented on displays (e.g., a cathoderay tube (CRT) or liquid crystal display (LCD) monitor), pointingdevices (e.g., a computer mouse or trackball), keyboards, keypads,touchpads, scanning devices, voice recognition devices, gesturerecognition devices, printers, audio speakers, microphones, cameras, orthe like. I/O devices 1060 may be connected to computer system 1000through a wired or wireless connection. I/O devices 1060 may beconnected to computer system 1000 from a remote location. I/O devices1060 located on remote computer system, for example, may be connected tocomputer system 1000 via a network and network interface 1040.

Network interface 1040 may include a network adapter that provides forconnection of computer system 1000 to a network. Network interface may1040 may facilitate data exchange between computer system 1000 and otherdevices connected to the network. Network interface 1040 may supportwired or wireless communication. The network may include an electroniccommunication network, such as the Internet, a local area network (LAN),a wide area network (WAN), a cellular communications network, or thelike.

System memory 1020 may be configured to store program instructions 1100or data 1110. Program instructions 1100 may be executable by a processor(e.g., one or more of processors 1010 a-1010 n) to implement one or moreembodiments of the present techniques. Instructions 1100 may includemodules of computer program instructions for implementing one or moretechniques described herein with regard to various processing modules.Program instructions may include a computer program (which in certainforms is known as a program, software, software application, script, orcode). A computer program may be written in a programming language,including compiled or interpreted languages, or declarative orprocedural languages. A computer program may include a unit suitable foruse in a computing environment, including as a stand-alone program, amodule, a component, or a subroutine. A computer program may or may notcorrespond to a file in a file system. A program may be stored in aportion of a file that holds other programs or data (e.g., one or morescripts stored in a markup language document), in a single filededicated to the program in question, or in multiple coordinated files(e.g., files that store one or more modules, sub programs, or portionsof code). A computer program may be deployed to be executed on one ormore computer processors located locally at one site or distributedacross multiple remote sites and interconnected by a communicationnetwork.

System memory 1020 may include a tangible program carrier having programinstructions stored thereon. A tangible program carrier may include anon-transitory computer readable storage medium. A non-transitorycomputer readable storage medium may include a machine readable storagedevice, a machine readable storage substrate, a memory device, or anycombination thereof. Non-transitory computer readable storage medium mayinclude non-volatile memory (e.g., flash memory, ROM, PROM, EPROM,EEPROM memory), volatile memory (e.g., random access memory (RAM),static random access memory (SRAM), synchronous dynamic RAM (SDRAM)),bulk storage memory (e.g., CD-ROM and/or DVD-ROM, hard-drives), or thelike. System memory 1020 may include a non-transitory computer readablestorage medium that may have program instructions stored thereon thatare executable by a computer processor (e.g., one or more of processors1010 a-1010 n) to cause the subject matter and the functional operationsdescribed herein. A memory (e.g., system memory 1020) may include asingle memory device and/or a plurality of memory devices (e.g.,distributed memory devices). Instructions or other program code toprovide the functionality described herein may be stored on a tangible,non-transitory computer readable media. In some cases, the entire set ofinstructions may be stored concurrently on the media, or in some cases,different parts of the instructions may be stored on the same media atdifferent times.

I/O interface 1050 may be configured to coordinate I/O traffic betweenprocessors 1010 a-1010 n, system memory 1020, network interface 1040,I/O devices 1060, and/or other peripheral devices. I/O interface 1050may perform protocol, timing, or other data transformations to convertdata signals from one component (e.g., system memory 1020) into a formatsuitable for use by another component (e.g., processors 1010 a-1010 n).I/O interface 1050 may include support for devices attached throughvarious types of peripheral buses, such as a variant of the PeripheralComponent Interconnect (PCI) bus standard or the Universal Serial Bus(USB) standard.

Embodiments of the techniques described herein may be implemented usinga single instance of computer system 1000 or multiple computer systems1000 configured to host different portions or instances of embodiments.Multiple computer systems 1000 may provide for parallel or sequentialprocessing/execution of one or more portions of the techniques describedherein.

Those skilled in the art will appreciate that computer system 1000 ismerely illustrative and is not intended to limit the scope of thetechniques described herein. Computer system 1000 may include anycombination of devices or software that may perform or otherwise providefor the performance of the techniques described herein. For example,computer system 1000 may include or be a combination of acloud-computing system, a data center, a server rack, a server, avirtual server, a desktop computer, a laptop computer, a tabletcomputer, a server device, a client device, a mobile telephone, apersonal digital assistant (PDA), a mobile audio or video player, a gameconsole, a vehicle-mounted computer, or a Global Positioning System(GPS), or the like. Computer system 1000 may also be connected to otherdevices that are not illustrated, or may operate as a stand-alonesystem. In addition, the functionality provided by the illustratedcomponents may in some embodiments be combined in fewer components ordistributed in additional components. Similarly, in some embodiments,the functionality of some of the illustrated components may not beprovided or other additional functionality may be available.

Those skilled in the art will also appreciate that while various itemsare illustrated as being stored in memory or on storage while beingused, these items or portions of them may be transferred between memoryand other storage devices for purposes of memory management and dataintegrity. Alternatively, in other embodiments some or all of thesoftware components may execute in memory on another device andcommunicate with the illustrated computer system via inter-computercommunication. Some or all of the system components or data structuresmay also be stored (e.g., as instructions or structured data) on acomputer-accessible medium or a portable article to be read by anappropriate drive, various examples of which are described above. Insome embodiments, instructions stored on a computer-accessible mediumseparate from computer system 1000 may be transmitted to computer system1000 via transmission media or signals such as electrical,electromagnetic, or digital signals, conveyed via a communication mediumsuch as a network or a wireless link. Various embodiments may furtherinclude receiving, sending, or storing instructions or data implementedin accordance with the foregoing description upon a computer-accessiblemedium. Accordingly, the present techniques may be practiced with othercomputer system configurations.

In block diagrams, illustrated components are depicted as discretefunctional blocks, but embodiments are not limited to systems in whichthe functionality described herein is organized as illustrated. Thefunctionality provided by each of the components may be provided bysoftware or hardware modules that are differently organized than ispresently depicted, for example such software or hardware may beintermingled, conjoined, replicated, broken up, distributed (e.g. withina data center or geographically), or otherwise differently organized.The functionality described herein may be provided by one or moreprocessors of one or more computers executing code stored on a tangible,non-transitory, machine readable medium. In some cases, notwithstandinguse of the singular term “medium,” the instructions may be distributedon different storage devices associated with different computingdevices, for instance, with each computing device having a differentsubset of the instructions, an implementation consistent with usage ofthe singular term “medium” herein. In some cases, third party contentdelivery networks may host some or all of the information conveyed overnetworks, in which case, to the extent information (e.g., content) issaid to be supplied or otherwise provided, the information may providedby sending instructions to retrieve that information from a contentdelivery network.

The reader should appreciate that the present application describesseveral independently useful techniques. Rather than separating thosetechniques into multiple isolated patent applications, applicants havegrouped these techniques into a single document because their relatedsubject matter lends itself to economies in the application process. Butthe distinct advantages and aspects of such techniques should not beconflated. In some cases, embodiments address all of the deficienciesnoted herein, but it should be understood that the techniques areindependently useful, and some embodiments address only a subset of suchproblems or offer other, unmentioned benefits that will be apparent tothose of skill in the art reviewing the present disclosure. Due to costsconstraints, some techniques disclosed herein may not be presentlyclaimed and may be claimed in later filings, such as continuationapplications or by amending the present claims. Similarly, due to spaceconstraints, neither the Abstract nor the Summary of the Inventionsections of the present document should be taken as containing acomprehensive listing of all such techniques or all aspects of suchtechniques.

It should be understood that the description and the drawings are notintended to limit the present techniques to the particular formdisclosed, but to the contrary, the intention is to cover allmodifications, equivalents, and alternatives falling within the spiritand scope of the present techniques as defined by the appended claims.Further modifications and alternative embodiments of various aspects ofthe techniques will be apparent to those skilled in the art in view ofthis description. Accordingly, this description and the drawings are tobe construed as illustrative only and are for the purpose of teachingthose skilled in the art the general manner of carrying out the presenttechniques. It is to be understood that the forms of the presenttechniques shown and described herein are to be taken as examples ofembodiments. Elements and materials may be substituted for thoseillustrated and described herein, parts and processes may be reversed oromitted, and certain features of the present techniques may be utilizedindependently, all as would be apparent to one skilled in the art afterhaving the benefit of this description of the present techniques.Changes may be made in the elements described herein without departingfrom the spirit and scope of the present techniques as described in thefollowing claims. Headings used herein are for organizational purposesonly and are not meant to be used to limit the scope of the description.

As used throughout this application, the word “may” is used in apermissive sense (i.e., meaning having the potential to), rather thanthe mandatory sense (i.e., meaning must). The words “include”,“including”, and “includes” and the like mean including, but not limitedto. As used throughout this application, the singular forms “a,” “an,”and “the” include plural referents unless the content explicitlyindicates otherwise. Thus, for example, reference to “an element” or “aelement” includes a combination of two or more elements, notwithstandinguse of other terms and phrases for one or more elements, such as “one ormore.” The term “or” is, unless indicated otherwise, non-exclusive,i.e., encompassing both “and” and “or.” Terms describing conditionalrelationships, e.g., “in response to X, Y,” “upon X, Y,”, “if X, Y,”“when X, Y,” and the like, encompass causal relationships in which theantecedent is a necessary causal condition, the antecedent is asufficient causal condition, or the antecedent is a contributory causalcondition of the consequent, e.g., “state X occurs upon condition Yobtaining” is generic to “X occurs solely upon Y” and “X occurs upon Yand Z.” Such conditional relationships are not limited to consequencesthat instantly follow the antecedent obtaining, as some consequences maybe delayed, and in conditional statements, antecedents are connected totheir consequents, e.g., the antecedent is relevant to the likelihood ofthe consequent occurring. Statements in which a plurality of attributesor functions are mapped to a plurality of objects (e.g., one or moreprocessors performing steps A, B, C, and D) encompasses both all suchattributes or functions being mapped to all such objects and subsets ofthe attributes or functions being mapped to subsets of the attributes orfunctions (e.g., both all processors each performing steps A-D, and acase in which processor 1 performs step A, processor 2 performs step Band part of step C, and processor 3 performs part of step C and step D),unless otherwise indicated. Similarly, reference to “a computer system”performing step A and “the computer system” performing step B caninclude the same computing device within the computer system performingboth steps or different computing devices within the computer systemperforming steps A and B. Further, unless otherwise indicated,statements that one value or action is “based on” another condition orvalue encompass both instances in which the condition or value is thesole factor and instances in which the condition or value is one factoramong a plurality of factors. Unless otherwise indicated, statementsthat “each” instance of some collection have some property should not beread to exclude cases where some otherwise identical or similar membersof a larger collection do not have the property, i.e., each does notnecessarily mean each and every. Limitations as to sequence of recitedsteps should not be read into the claims unless explicitly specified,e.g., with explicit language like “after performing X, performing Y,” incontrast to statements that might be improperly argued to imply sequencelimitations, like “performing X on items, performing Y on the X'editems,” used for purposes of making claims more readable rather thanspecifying sequence. Statements referring to “at least Z of A, B, andC,” and the like (e.g., “at least Z of A, B, or C”), refer to at least Zof the listed categories (A, B, and C) and do not require at least Zunits in each category. Unless specifically stated otherwise, asapparent from the discussion, it is appreciated that throughout thisspecification discussions utilizing terms such as “processing,”“computing,” “calculating,” “determining” or the like refer to actionsor processes of a specific apparatus, such as a special purpose computeror a similar special purpose electronic processing/computing device.Features described with reference to geometric constructs, like“parallel,” “perpendicular/orthogonal,” “square”, “cylindrical,” and thelike, should be construed as encompassing items that substantiallyembody the properties of the geometric construct, e.g., reference to“parallel” surfaces encompasses substantially parallel surfaces. Thepermitted range of deviation from Platonic ideals of these geometricconstructs is to be determined with reference to ranges in thespecification, and where such ranges are not stated, with reference toindustry norms in the field of use, and where such ranges are notdefined, with reference to industry norms in the field of manufacturingof the designated feature, and where such ranges are not defined,features substantially embodying a geometric construct should beconstrued to include those features within 15% of the definingattributes of that geometric construct. The terms “first”, “second”,“third,” “given” and so on, if used in the claims, are used todistinguish or otherwise identify, and not to show a sequential ornumerical limitation. As is the case in ordinary usage in the field,data structures and formats described with reference to uses salient toa human need not be presented in a human-intelligible format toconstitute the described data structure or format, e.g., text need notbe rendered or even encoded in Unicode or ASCII to constitute text;images, maps, and data-visualizations need not be displayed or decodedto constitute images, maps, and data-visualizations, respectively;speech, music, and other audio need not be emitted through a speaker ordecoded to constitute speech, music, or other audio, respectively.Computer implemented instructions, commands, and the like are notlimited to executable code and can be implemented in the form of datathat causes functionality to be invoked, e.g., in the form of argumentsof a function or API call.

In this patent, to the extent any U.S. patents, U.S. patentapplications, or other materials (e.g., articles) have been incorporatedby reference, the text of such materials is only incorporated byreference to the extent that no conflict exists between such materialand the statements and drawings set forth herein. In the event of suchconflict, the text of the present document governs, and terms in thisdocument should not be given a narrower reading in virtue of the way inwhich those terms are used in other materials incorporated by reference.

The present techniques will be better understood with reference to thefollowing enumerated embodiments:

-   1. A method, comprising: obtaining, with a computer system, test    data that quantifies a patient's cardiovascular status, the test    data specifying patient attributes in a plurality of cardiovascular    dimensions of the patient, a first subset of the plurality of    cardiovascular dimensions being independent cardiovascular    dimensions and a second subset of the plurality of dimensions being    dependent cardiovascular dimensions; determining, with the computer    system, a plurality of normalized differences between the test data    and target criteria in each of the cardiovascular dimensions, the    plurality of normalized differences quantifying different aspects of    hypertension of the patient; determining, with the computer system,    predicted-effect vectors of each of a plurality of different classes    of pharmaceuticals having hypertension as an indication, wherein:    the predicted-effect vectors each correspond to a different    respective class of pharmaceuticals among the different classes of    pharmaceuticals, the predicted-effect vectors each have a plurality    of values quantifying respective effects of the corresponding class    of pharmaceuticals on corresponding dimensions among a third set of    the cardiovascular dimensions of the patient, the values are each    based on both the corresponding normalized differences of the    corresponding dimension among the third set and a respective    strength of effect of the corresponding class of pharmaceuticals on    the corresponding dimension, the respective strength effects are    determined based on respective multi-dimensional models of the    corresponding class of pharmaceuticals, and the third set at least    overlaps with the first subset and the second subset; determining,    with the computer system, an aggregate score for each respective    class of pharmaceuticals among the different classes of    pharmaceuticals based on values of the corresponding    predicted-effect vectors of the corresponding class of    pharmaceuticals; ranking, with the computer system, the different    classes of pharmaceuticals based on the aggregate scores to form a    ranked list of the different classes of pharmaceuticals; and    outputting, with the computer system, based on the ranking, a    recommended sequence of the classes of pharmaceuticals to administer    to the patient.-   2. The method of embodiment 1, comprising: accessing, with the    computer system, pair-wise compatibilities of the different classes    of pharmaceuticals; and detecting, based on the -wise    compatibilities, incompatible pairs of the different classes of    pharmaceuticals in the ranked list; and removing, with the computer    system, from the ranked list, at least one member of each detected    incompatible pair to form a filtered, ranked list.-   3. The method of embodiment 2, wherein: removing, with the computer    system, at least one member from each detected pair comprises    removing a lower-ranking member from each detected pair.-   4. The method of embodiment 2, wherein forming a filtered, ranked    list comprises obtaining, with the computer system, comorbidities or    demographic information of the patient; and adjusting, with the    computer system, the filtered, ranked list based on the obtained    comorbidities or demographic information.-   5. The method of embodiment 4, comprising: causing, with the    computer system, a user interface to be presented, the user    interface indicating a warning for a given one of the classes of    pharmaceuticals in response to the comorbidities or demographic    information.-   6. The method of embodiment 2, comprising: administering a first    class of pharmaceuticals at a first ranking in the filtered, ranked    list; and after administering the first class of pharmaceuticals,    administering a second class of pharmaceuticals at a second ranking    in the filtered, ranked list, the second ranking being lower in the    ranking than the first ranking.-   7. The method of any one of embodiments 1-6 comprising: obtaining,    with the computer system, a comorbidity or demographic attribute of    the patient, wherein: a given one of the values of a given one of    the predicted-effect vectors is based on the comorbidity or    demographic attribute, at least some of the values of the given one    of the predicted-effect vectors are not affected by the comorbidity    or the demographic attribute, and at least some of the    predicted-effect vectors are not affected by the comorbidity or the    demographic attribute.-   8. The method of any one of embodiments 1-7, wherein: the ranking is    based on predicted-effect vector values corresponding to each of the    first subset of dimensions.-   9. The method of embodiment 8, wherein: the ranking is not based on    predicted-effect vector values corresponding to any of the second    subset of dimensions.-   10. The method of embodiment 8, wherein: the first subset of    dimensions includes at least two of the following dimensions:    systolic blood pressure, pulse pressure, cardiac index, or heart    rate.-   11. The method of embodiment 8, wherein: the first subset of    dimensions includes each of the following dimensions: systolic blood    pressure, pulse pressure, cardiac index, and heart rate.-   12. The method of any one of embodiments 1-11, wherein the classes    of pharmaceuticals include at least six of the following: Diuretics,    Beta-blockers, ACE inhibitors, Angiotensin II receptor blockers,    Calcium channel blockers, Alpha blockers, Alpha-2 Receptor Agonists,    Combined alpha and beta-blockers, Central agonists, Peripheral    adrenergic inhibitors, or Vasodilators.-   13. The method of any one of embodiments 1-11, wherein the classes    of pharmaceuticals include each of the following: Diuretics,    Beta-blockers, ACE inhibitors, Angiotensin II receptor blockers,    Calcium channel blockers, Alpha blockers, Alpha-2 Receptor Agonists,    Combined alpha and beta-blockers, Central agonists, Peripheral    adrenergic inhibitors, and Vasodilators.-   14. The method of any one of embodiments 1-13, wherein at least some    of the plurality of normalized differences are z-scores specifying a    number of standard deviations a corresponding patient attribute is    in the test data from a mean of a population.-   15. The method of any one of embodiments 1-13, wherein a given one    of the aggregate scores for a given one of the classes of    pharmaceuticals is based on a weighted sum of the values of the    corresponding predicted-effect vector of the given one of the    classes of pharmaceuticals.-   16. The method of any one of embodiments 1-15, wherein at least some    of the values are each based on products of the corresponding    normalized differences of the corresponding dimension among the    third set and the respective strength of effect of the corresponding    class of pharmaceuticals on the corresponding dimension.-   17. The method of any one of embodiments 1-16, wherein a given    multi-dimensional model of a given one of the classes of    pharmaceuticals specifies a non-planar surface in five or higher    dimensions, the five or higher dimension comprising: an output    dimension corresponding to an effect strength of the given one of    the classes of pharmaceuticals, and four or more of the    cardiovascular dimensions of the patient.-   18. The method of any one of embodiments 1-17, comprising:    repeating, with the computer system, the method of embodiment 1 with    an updated instance of the test data obtained after administering    part of the sequence of the classes of pharmaceuticals to the    patient; and as a result of the repeating, changing, with the    computer system, the sequence.-   19. A tangible, non-transitory, machine-readable medium storing    instructions that when executed by a data processing apparatus cause    the data processing apparatus to perform operations comprising: the    computer-implemented operations of any one of embodiments 1-18.-   20. A system, comprising: one or more processors; and memory storing    instructions that when executed by the processors cause the    processors to effectuate operations comprising: the    computer-implemented operations of any one of embodiments 1-18.

What is claimed is:
 1. A method, comprising: obtaining, with a computersystem, test data that quantifies a patient's cardiovascular status, thetest data specifying patient attributes in a plurality of cardiovasculardimensions of the patient, a first subset of the plurality ofcardiovascular dimensions being independent cardiovascular dimensionsand a second subset of the plurality of dimensions being dependentcardiovascular dimensions; determining, with the computer system, aplurality of normalized differences between the test data and targetcriteria in each of the cardiovascular dimensions, the plurality ofnormalized differences quantifying different aspects of hypertension ofthe patient; determining, with the computer system, predicted-effectvectors of each of a plurality of different classes of pharmaceuticalshaving hypertension as an indication, wherein: the predicted-effectvectors each correspond to a different respective class ofpharmaceuticals among the different classes of pharmaceuticals, thepredicted-effect vectors each have a plurality of values quantifyingrespective effects of the corresponding class of pharmaceuticals oncorresponding dimensions among a third set of the cardiovasculardimensions of the patient, the values are each based on both thecorresponding normalized differences of the corresponding dimensionamong the third set and a respective strength of effect of thecorresponding class of pharmaceuticals on the corresponding dimension,the respective strength effects are determined based on respectivemulti-dimensional models of the corresponding class of pharmaceuticals,and the third set at least overlaps with the first subset and the secondsubset; determining, with the computer system, an aggregate score foreach respective class of pharmaceuticals among the different classes ofpharmaceuticals based on values of the corresponding predicted-effectvectors of the corresponding class of pharmaceuticals; ranking, with thecomputer system, the different classes of pharmaceuticals based on theaggregate scores to form a ranked list of the different classes ofpharmaceuticals; and outputting, with the computer system, based on theranking, a recommended sequence of the classes of pharmaceuticals toadminister to the patient.
 2. The method of claim 1, comprising:accessing, with the computer system, pair-wise compatibilities of thedifferent classes of pharmaceuticals; and detecting, based on thepair-wise compatibilities, incompatible pairs of the different classesof pharmaceuticals in the ranked list; and removing, with the computersystem, from the ranked list, at least one member of each detectedincompatible pair to form a filtered, ranked list.
 3. The method ofclaim 2, wherein: removing, with the computer system, at least onemember from each detected pair comprises removing a lower-ranking memberfrom each detected pair.
 4. The method of claim 2, wherein forming afiltered, ranked list comprises obtaining, with the computer system,comorbidities or demographic information of the patient; and adjusting,with the computer system, the filtered, ranked list based on theobtained comorbidities or demographic information.
 5. The method ofclaim 4, comprising: causing, with the computer system, a user interfaceto be presented, the user interface indicating a warning for a given oneof the classes of pharmaceuticals in response to the comorbidities ordemographic information.
 6. The method of claim 2, comprising:administering a first class of pharmaceuticals at a first ranking in thefiltered, ranked list; and after administering the first class ofpharmaceuticals, administering a second class of pharmaceuticals at asecond ranking in the filtered, ranked list, the second ranking beinglower in the ranking than the first ranking.
 7. The method of claim 1comprising: obtaining, with the computer system, a comorbidity ordemographic attribute of the patient, wherein: a given one of the valuesof a given one of the predicted-effect vectors is based on thecomorbidity or demographic attribute, at least some of the values of thegiven one of the predicted-effect vectors are not affected by thecomorbidity or the demographic attribute, and at least some of thepredicted-effect vectors are not affected by the comorbidity or thedemographic attribute.
 8. The method of claim 1, wherein: the ranking isbased on predicted-effect vector values corresponding to each of thefirst subset of dimensions.
 9. The method of claim 8, wherein: theranking is not based on predicted-effect vector values corresponding toany of the second subset of dimensions.
 10. The method of claim 8,wherein: the first subset of dimensions includes at least two of thefollowing dimensions: systolic blood pressure, pulse pressure, cardiacindex, or heart rate.
 11. The method of claim 8, wherein: the firstsubset of dimensions includes each of the following dimensions: systolicblood pressure, pulse pressure, cardiac index, and heart rate.
 12. Themethod of claim 1, wherein the classes of pharmaceuticals include atleast six of the following: Diuretics, Beta-blockers,Angiotensin-converting enzyme (ACE) inhibitors, Angiotensin II receptorblockers (ARBs), Calcium channel blockers, Alpha blockers, Alpha-2Receptor Agonists, Combined alpha and beta-blockers, Central agonists,Peripheral adrenergic inhibitors, or Vasodilators.
 13. The method ofclaim 1, wherein the classes of pharmaceuticals include each of thefollowing: Diuretics, Beta-blockers, ACE inhibitors, ARBs, Calciumchannel blockers, Alpha blockers, Alpha-2 Receptor Agonists, Combinedalpha and beta-blockers, Central agonists, Peripheral adrenergicinhibitors, and Vasodilators.
 14. The method of claim 1, wherein atleast some of the plurality of normalized differences are z-scoresspecifying a number of standard deviations a corresponding patientattribute is in the test data from a mean of a population.
 15. Themethod of claim 1, wherein a given one of the aggregate scores for agiven one of the classes of pharmaceuticals is based on a weighted sumof the values of the corresponding predicted-effect vector of the givenone of the classes of pharmaceuticals.
 16. The method of claim 1,wherein at least some of the values are each based on products of thecorresponding normalized differences of the corresponding dimensionamong the third set and the respective strength of effect of thecorresponding class of pharmaceuticals on the corresponding dimension.17. The method of claim 1, wherein a given multi-model of a given one ofthe classes of pharmaceuticals specifies a non-planar surface in five orhigher dimensions, the five or higher dimension comprising: an outputdimension corresponding to an effect strength of the given one of theclasses of pharmaceuticals, and four or more of the cardiovasculardimensions of the patient.
 18. The method of claim 1, comprising: stepsfor determining a sequence of classes of pharmaceuticals to administerto a patient.
 19. The method of claim 1, comprising: repeating, with thecomputer system, the method of claim 1 with an updated instance of thetest data obtained after administering part of the sequence of theclasses of pharmaceuticals to the patient; and as a result of therepeating, changing, with the computer system, the sequence.
 20. Themethod of claim 1, wherein: the multi-dimensional models are artificialintelligence models that are more data efficient than machine learningmodels and less brittle than expert systems; at least some of themulti-dimensional models are interaction models that model interactionsbetween classes of pharmaceuticals; at least some of themulti-dimensional models encodes a five or higher dimensional surfaceindicating effects of the corresponding class of pharmaceuticals; and atleast some of the multi-dimensional models are trained with Markov chainMonte Carlo.
 21. The method of claim 1, wherein: the multi-dimensionalmodels are artificial intelligence models that are more data efficientthan machine learning models and less brittle than expert systems; atleast some of the multi-dimensional models are interaction models thatmodel interactions between classes of pharmaceuticals; and at least someof the multi-dimensional models encodes a four or higher dimensionalsurface indicating effects of the corresponding class ofpharmaceuticals.
 22. The method of claim 1, wherein: at least some ofthe multi-dimensional models are interaction models that modelinteractions between classes of pharmaceuticals; and at least some ofthe multi-dimensional models encodes a five or higher dimensionalsurface indicating effects of the corresponding class ofpharmaceuticals.
 23. The method of claim 1, wherein determiningnormalized differences comprises steps for determining normalizeddifferences.
 24. A tangible, non-transitory, machine-readable mediumstoring instructions that when executed by one or more processorseffectuate operations comprising: obtaining, with a computer system,test data stored in Synchronous Dynamic Random Access Memory thatquantifies a patient's cardiovascular status, the test data specifyingpatient attributes in a plurality of cardiovascular dimensions of thepatient, a first subset of the plurality of cardiovascular dimensionsbeing independent cardiovascular dimensions and a second subset of theplurality of dimensions being dependent cardiovascular dimensions;determining, with the computer system, a plurality of normalizeddifferences between the test data and target criteria in each of thecardiovascular dimensions, the plurality of normalized differencesquantifying different aspects of hypertension of the patient;determining, with the computer system, predicted-effect vectors of eachof a plurality of different classes of pharmaceuticals havinghypertension as an indication, wherein: the predicted-effect vectorseach correspond to a different respective class of pharmaceuticals amongthe different classes of pharmaceuticals, the predicted-effect vectorseach have a plurality of values quantifying respective effects of thecorresponding class of pharmaceuticals on corresponding dimensions amonga third set of the cardiovascular dimensions of the patient, the valuesare each based on both the corresponding normalized differences of thecorresponding dimension among the third set and a respective strength ofeffect of the corresponding class of pharmaceuticals on thecorresponding dimension, the respective strength effects are determinedbased on respective multi-dimensional models of the corresponding classof pharmaceuticals, and the third set at least overlaps with the firstsubset and the second sub set; determining, with the computer system, anaggregate score for each respective class of pharmaceuticals among thedifferent classes of pharmaceuticals based on values of thecorresponding predicted-effect vectors of the corresponding class ofpharmaceuticals; ranking, with the computer system, the differentclasses of pharmaceuticals based on the aggregate scores to form aranked list of the different classes of pharmaceuticals; and outputting,with the computer system, based on the ranking, a recommended sequenceof the classes of pharmaceuticals to administer to the patient.